|
|
|
|
Upgrading To SftTabs/NET 6.0 |
SftTabs/NET 6.0 is upward compatible to earlier versions making upgrading a simple process.
Multiple versions of SftTabs/NET can be used on the same system without any problems. Only one version can be used in one application.
If you have developed an application with an earlier version of the product, you can of course continue to use the earlier version.
Before opening a project that uses SftTabs/NET 5.5 or 6.0, make sure to create a backup of all projects.
Upgrading To SftTabs/NET 6.0 With VB
Upgrading To SftTabs/NET 6.0 With C#
Keeping SftTabs/NET 5.5 With VB
Keeping SftTabs/NET 5.5 With C#
Required Application Changes With SftTabs/NET 6.0
There are just a few features that won't convert from 5.5 to 6.0. You will have to manually convert these, by taking advantage of the new product features:
SftTabs/NET 5.x |
SftTabs/NET 6.0 Equivalent Feature |
Tab styles with automatic vertical text alignment (Style property) will not automatically show vertical text after conversion. |
In order to achieve the same vertical text orientation, use the Angle property (90 or 270 degrees) for each tab's text component. Access the property pages, click on "Tabs", select the desired tab in the "List of Tabs", then click the "Edit Selected Tab..." button. This allows you to select each "part" on the tab and fine-tune its properties. On the right hand side, click on the TextPartClass part. Below (in the "Currently Selected Parts Properties") look for the Angle property and change it as desired, then click Close, followed by Apply. Repeat for all desired tabs. |
Transparency for images based on bitmaps has been discontinued. |
If image transparency is desired, images based on GIF or PNG files should be used instead, allowing for transparent and translucent images (with alpha channel). |
ScrollButtonStyle.Scroll has been dropped. |
The new, equivalent ScrollButtonStyle.Themed should be used instead. |
The current tab is no longer saved (Current property). |
After converting forms to 6.0, the initially selected tab must be defined using the InitialTab property, which defaults to -1. |
The Tab type should no longer be used. |
Use the equivalent TabClass type instead. The TabClass no longer offers a public constructor. Instead, the Add or Insert methods should be used to obtain a TabClass instance. |
The TabCollection type should no longer be used. |
Use the equivalent TabCollectionClass type instead. |
The Scrolling type should no longer be used. |
Use the equivalent ScrollingClass type instead. |